Repository navigation
Honor hidden details marker pseudo - #784
Merged
Merged
Conversation
This was referenced Sep 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WebScene already retains one list-marker layout/paint path for
<summary>, but it dropped the two::-webkit-details-marker { display:none }rules authored by unchanged Code OSS Chat. This change gives that selector a bounded pseudo kind, stores one lazy hidden bit, includes it in layout equality, and suppresses the existing marker at its single text/geometry source.The authored native contract covers selector classification, visible/hide/restore behavior and a non-summary zero-allocation guard. A browser/native reftest compares the pseudo-hidden result with the established
list-style:nonereference. No second marker representation, DOM node, timer, document scan, or frame demand is added.Validation was not executed under the current implementation-throughput direction; evidence remains zero until the focused pixel, mutation, high-count performance, lifecycle and package gates run.
Closes #783
Refs #237
Refs #235